-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create tests for basic hashing; add an API to create opaque pointers #879
Conversation
91ca44d
to
1359bb5
Compare
bbced04
to
dc3a61f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This PR is a strict improvement.
However, I think it's worth thinking about the places where we could demonstrate the notion of opaque pointers, which I like to think of as non-dereferenceable data:
- the
Write
instance for the Lurk alphaPtr
shows specific typed structure, we'll think whether it's worth integrating such a thing in our pointer representation as we work through the related issue of Support type predicates #658. - Indeed if I look at the difference between this and the Lurk alpha
Opaque
, the tag is the main difference:
https://github.com/lurk-lab/lurk-rs/blob/dae0d6c478a83c80e3b3753c29f89e4ecd2a6313/src/ptr.rs#L94-L100 - for now, we can integrate the opaque vocabulary, and probably this function's name in the lem tests
hide_opaque_open_available
.
dc3a61f
to
0d05a95
Compare
0d05a95
to
cd91549
Compare
cd91549
to
73519aa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot!
This PR is a follow up to #878 because I realized that we didn't have tests for the basic cases of
Store::hash_ptr
.This PR also shows how to achieve opaque functionality with
ZPtr
s.